[API 37] Regenerate .NET for Android API documentation - #643

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

The API 37 regeneration drops authored documentation for at least 21 unchanged, signature-matched members across seven files, replacing real summaries/returns/remarks with To be added.. Confirmed examples include parcelable members in NetworkRegistrationInfo, PhysicalChannelConfig, and SubscriptionInfo; TelephonyManager request/radio-family members; six NetworkRegistrationInfoServiceType values; three PhoneNumberSource values; and AccessibleObject.IsAnnotationPresent. Please restore the main-branch prose and add a full signature-keyed preservation check so unchanged members cannot lose authored documentation.

Three completeness blockers remain in the API 37 regeneration:

• A full Android 37 source/signature audit finds 644 new API owners across 159 files still missing 1,179 source-documented elements (14 type descriptions, 623 member descriptions, 159 returns, and 383 parameters), including HealthPermissions.ReadActivityIntensity, String.SplitWithDelimiters, Notification.Metric.FixedTime, and PrinterInfo.Builder.SetSetupIntent.
• Preservation still drops 49 substantive base elements: 48 type-level summaries/remarks across 46 matched types plus the unchanged ActivityManager.GetRecentTasks summary.
• Removing IInputType leaves four exact-head broken xrefs, and OpenPublishing reports 27 deleted public destinations without redirects.

Please repair the API 37 source import, extend preservation to type-level docs and the missing member summary, update stale references, and add redirects/historical handling for every removed destination.

The API 37 output still has four independent blockers:

1. The regeneration erases existing current documentation. A signature-keyed preservation audit finds at least 283 direct substantive channels across 68 current XML files replaced by To be added. or removed. For example, RegexOptions.xml:243-246 erases the current UnicodeCharacterClass field summary, while AppInfo.xml:173-176 replaces the existing DescribeContents summary, return and remarks. Preserve all signature-matched base documentation before importing API 37 content and rerun the preservation audit.

2. --api-since 37 omits platform-versioned API 37 owners that lack a literal ApiSince=37. SelectOwners gates every owner through HasApiSince, which only recognizes the register attribute. There are 445 current direct owners marked SupportedOSPlatform("android37.0") without that attribute whose summaries remain placeholders; AppSearchResultCode.Unavailable is a direct JNI-mapped example. Include exact platform-version availability (and applicable type inheritance) in selection, then rerun the API 37 completeness import.

3. The retained historical framework indexes reference member DocIds removed from the documentation set. net-android-35.0.xml:84250-84254 still lists the CallType CallControl.Answer and RequestVideoState identities, but CallControl.xml:57-60 retains only the distinct System.Int32 signature. The same mismatch remains for the old JniValueManager.ActivatePeer ID. Preserve appropriate historical member records or add compatible member redirects so the versioned API inventory resolves.

4. InputType directs users to a removed current API. InputType.xml:20 says to use Android.Text.IInputType, but the current inventory contains InputTypes and no IInputType; the new redirect also targets InputTypes. Correct the obsolete guidance in the generated signature/source or retain a valid current IInputType API.

Current API records still lose preserved documentation after signature projection. AppFunctionManager.SetAppFunctionEnabled:662-705 retains the same JNI identity after AppFunctionState became AppFunctionEnabledState, but all parameters, summary, and remarks are placeholders. ActivityManager.GetRecentTasks also replaces its exact-DocId summary with an empty element, and current CallControl.Answer/RequestVideoState forms retain placeholder remarks while prose exists only on historical alternates. Match active replacement records by stable JNI identity, treat empty elements as regressions, and restore base documentation to the current signatures.

Re-reviewed the complete 2,237-file revision 7ac03ee5d2f825f6e86a10c2e5dcc0a807eb4e22, including the generated corpus and publication paths. The latest SetAppFunctionEnabled, GetRecentTasks, and active CallControl preservation examples are fixed. Three blockers remain:

1. Preserve substantive documentation when regenerated text is nonempty but unusable. Forty-four exact-identity summaries across 19 files now contain slash separators or { instead of their existing descriptions, for example CharSequenceTransformation.xml:140-144. Twenty additional publish-relevant remarks channels lose nonredundant contract prose; NfcAdapter.xml:3412-3414 is one example where Android Beam availability/lifecycle/callback guidance becomes attribution alone. Restore these base channels and extend preservation validation beyond empty elements and To be added. to syntax-only and attribution-only replacements. The complete affected inventory is below.

2. Make the five retained historical method destinations publishable or redirect them. PdfPagePathObject.SetFillColor/SetStrokeColor, PdfPageTextObject.SetFillColor/SetStrokeColor, and JniRuntime.JniValueManager.TryConstructPeer have restored XML records but are absent from all three framework inventories (see net-android-36.0.xml:27917-27922). A signature's FrameworkAlternate alone does not retain the destination: ECMA2Yaml's member filter requires framework-index membership, and the exact-head publishing report confirms all five destinations are deleted without redirection. Add appropriate historical inventory membership or effective redirects for the emitted member destinations.

3. Attach app-function parameter descriptions to the actual managed names. IAppFunction.OnExecuteAppFunction:69-77 declares p0, p1, and p2, whose matching documentation remains To be added.. The imported prose is instead under nonexistent parameter names request, cancellationSignal, and callback. Publication looks up descriptions by the managed parameter name, so the real parameters remain undocumented, including the requirement that the callback complete exactly once. Move the existing descriptions to the verified p0/p1/p2 correspondence and remove the unmatched duplicate keys; the JNI argument order matches the immutable AOSP declaration.

These additional failures already exist at 15bc49bf089049beed2fa1b642b91d897171e6b0: they are earlier review-completeness misses, not newly introduced regressions in the latest update. None requires broadening the accepted conservative source-import policy.

The review used complete immutable base/head comparisons, authoritative source checks, independent XML reductions, and static publication-path tracing; downloaded PR code was not executed.

Re-reviewed the complete current PR at d7b005cb3d89f4a352ad005274cd00b51fc09644. All 44 summaries and 20 remarks are restored exactly from the immutable base. The five historical methods now have unique, correctly parented framework membership and no longer appear in the publishing deletion diagnostics. IAppFunction descriptions bind correctly to p0/p1/p2, retaining the exactly-once callback requirement.

Earlier preservation, API-37 availability, history and cross-reference fixes remain intact, and the accepted conservative source policy is unchanged. No high-confidence blocking issues remain.